Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | NetskopeClientStatus |
| Publisher | Netskope |
| Used in Solutions | Netskopev2 |
| Collection Method | CCF |
| Connector Definition Files | NetskopeClientStatus_ConnectorDefinition.json |
| DCR Definition Files | NetskopeClientStatus_DCR.json |
| CCF Configuration | NetskopeClientStatus_Poller.json |
| CCF Capabilities | APIKey |
| Microsoft Learn | View on Learn |
The Netskope Client Status connector ingests Netskope client device status records (installation, connectivity, health, and last-seen posture events) into Microsoft Sentinel via the Codeless Connector Framework (CCF) REST API poller. Data is delivered by the Netskope API as CSV and stored in the NetskopeClientStatus_CL table. Enumeration codes are retained in their original columns and translated during ingestion into adjacent human-readable *_name columns.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
NetskopeClientStatus_CL |
✗ | ✓ | ✗ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. STEP 1 - Create a Netskope API key.
Follow the Netskope documentation for guidance on this step.
2. STEP 2 - Create a Client Status iterator
Client Status does not support the shared index= convention used by the other Netskope event types — you must create a dedicated iterator for this data type before Microsoft Sentinel can poll it. Using the Netskope REST API v2 iterator endpoints, call the Create Iterator API once (for example POST https://<your-org>/api/v2/dataexport/iterator/<a-name-you-choose>?eventtype=clientstatus with your API token) and record the iterator name/ID you used — you will enter it below. Confirm the exact request shape against the linked Netskope documentation, as iterator management is a separate API surface from the events you are polling.
3. STEP 3 - Enter your Netskope product Details
Enter your Netskope organisation url, API Token, and the Client Status iterator ID you created in Step 2:
4. STEP 4 - Click Connect
Verify all fields above were filled in correctly. Press the Connect to connect Netskope to Microsoft Sentinel.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊